The next step in this process involves detailed analysis of the maintenance change requests. In case the maintenance change
request involves a minor enhancement, the identified list of impacted technology configuration items should be ratified and
the changes to be made should be detailed out. In case of the maintenance change request is a bug, analysis must be done to
identify the root cause, impacted technology configuration items and the actions needed to fix the same. During this
analysis, the Delivery Team must also check the list of technology defects (from the development teams) to check if the
defect and its workaround are already known. Study should also be carried out to check if a similar maintenance change
request has been executed earlier, and documentation for the same is available. In case no previous records are available,
the Delivery Team should proceed with the detailed analysis of the maintenance change request.
Next an impact analysis to analyze the potential consequences of the deployed changes in the application or system, must be
done. This helps to identify the various modules or parts of the system affected because of the change, changes to
interface requirements and impact to all third party impacted applications, etc. The Delivery Team should document all
analysis details in the Maintenance Change Request Analysis And Design Change Document. In case a scope change occurs
at this stage, the initial estimates must be revised to align with the new scope. If there is a change in schedule as per
the initial estimates, an approval must be obtained from the Client on the revised schedules.
|
